-
Notifications
You must be signed in to change notification settings - Fork 771
Docs for --scheduler-override-broadcast-host-port
#4721
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Albert Callarisa <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've left two suggestions
@@ -46,6 +46,7 @@ dapr init [flags] | |||
| `--container-runtime` | | `docker` | Used to pass in a different container runtime other than Docker. Supported container runtimes are: `docker`, `podman` | | |||
| `--dev` | | | Creates Redis and Zipkin deployments when run in Kubernetes. | | |||
| `--scheduler-volume` | | | Self-hosted only. Optionally, you can specify a volume for the scheduler service data directory. By default, without this flag, scheduler data is not persisted and not resilient to restarts. | | |||
| `--scheduler-override-broadcast-host-port` | | | Self-hosted only. Specify the scheduler broadcast host and port, for example: 192.168.42.42:50006. If not specified, it uses localhost:50006 (6060 for Windows). | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| `--scheduler-override-broadcast-host-port` | | | Self-hosted only. Specify the scheduler broadcast host and port, for example: 192.168.42.42:50006. If not specified, it uses localhost:50006 (6060 for Windows). | | |
| `--scheduler-override-broadcast-host-port` | | localhost:50006 (6060 for Windows) | Self-hosted only. Specify the scheduler broadcast host and port, for example: 192.168.42.42:50006. | |
|
||
This is necessary when you have to connect to the scheduler using a different host and port, as the scheduler only allows connections matching this host and port. | ||
|
||
By default, the scheduler will use localhost:50006 (6060 for Windows), as it's the most common way to connect to the scheduler. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By default, the scheduler will use localhost:50006 (6060 for Windows), as it's the most common way to connect to the scheduler. | |
By default, the scheduler will use localhost:50006 (6060 for Windows). |
Signed-off-by: Albert Callarisa <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:
In addition, please fill out the following to help reviewers understand this pull request:
Description
Added docs for the new
dapr init
self-hosted setting--scheduler-override-broadcast-host-port
.Issue reference
Implementation PR (and 1.15 patch):
dapr/cli#1520
dapr/cli#1521